Binding server accounts

ABSTRACT

One or more embodiments of the present specification relate to a data processing method for binding server accounts. An example method includes, in response to obtaining a binding request, determining a first account, and sending binding request feedback data to a terminal device. In response to obtaining binding object selection data that indicates a selection of candidate binding objects presented by the terminal device, a respective target binding object is determined for each selected candidate binding object, and a respective target server is determined for each target binding object. For each target server, the first account is bound to a second account of the target server.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/363,408, filed on Jun. 30, 2021, now allowed, which claims priorityto Chinese Patent Application No. 202011039604.9, filed on Sep. 28,2020, both of which are hereby incorporated by reference in theirentirety.

TECHNICAL FIELD

The present application relates to the field of computer technologies,and in particular, to methods, apparatuses, devices, and media for dataprocessing and resource transfer.

BACKGROUND

In existing technologies, people can use a variety of Internet servicesthrough Internet accounts. Some Internet services enable users to binddifferent Internet accounts to satisfy service needs or to improve userexperience.

SUMMARY

Embodiments of the present specification provide methods, apparatuses,devices, and media for data processing, resource transfer, and payment,so as to solve the technical problem of how to more efficiently processdata related to an account binding service.

To solve the above-mentioned technical problem, the embodiments of thepresent specification provide the following technical solutions.

Some embodiments of the present specification provide a first dataprocessing method, applied to a first server, including the following:obtaining a user binding request sent by a terminal device, determininga first to-be-bound account on the first server, and sending userbinding request feedback data to the terminal device so that theterminal device displays candidate binding objects; obtaining bindingobject selection data sent by the terminal device, determiningrespective target binding objects based on the binding object selectiondata, and determining one or more target servers among serverscorresponding to each of the respective target binding objects; andbinding the first account to a second account on each target server, andsending an account binding request to each target server so that thetarget server binds the second account on the target server to the firstaccount, where the second account corresponds to the same user identitydata as the first account.

Some embodiments of the present specification provide a second dataprocessing method, applied to a second server, including the following:if an identity authentication request or a binding consulting requestsent by a first server is obtained, where the identity authenticationrequest or the binding consulting request includes user identity datacorresponding to a first account, determining a second account on thesecond server corresponding to the same user identity data as the firstaccount, where the first account is an account on the first server;sending authentication feedback data or consultation feedback data tothe first server, where the authentication feedback data or theconsultation feedback data includes account data of the second account,so that the first server determines one or more target servers and sendsan account binding request to each target server; and if the accountbinding request sent by the first server is obtained, binding the secondaccount to the first account.

Some embodiments of the present specification provide a first resourcetransfer method, applied to a third server, including the following:obtaining a first resource transfer request sent by a terminal device,and determining a third account and a fourth account for which resourcetransfer is to be performed, and a resource transfer amount, where thethird account is an account on the third server, and the third accountis bound to the fourth account by using the above-mentioned first orsecond data processing method; and sending a second resource transferrequest to a fourth server on which the fourth account is located, sothat the fourth server decreases a resource of the fourth account by theresource transfer amount; obtaining resource transfer feedback data sentby the fourth server, and if it is determined, based on the resourcetransfer feedback data, that the resource of the fourth account isdecreased by the resource transfer amount, increasing a resource of thethird account by the resource transfer amount; or decreasing a resourceof the third account by the resource transfer amount, and sending asecond resource transfer request to a fourth server on which the fourthaccount is located, so that the fourth server increases a resource ofthe fourth account by the resource transfer amount.

Some embodiments of the present specification provide a second resourcetransfer method, applied to a fourth server, including the following: ifa resource transfer request sent by a third server is obtained,determining a fourth account on the fourth server for which resourcetransfer is to be performed, and determining a resource transfer amount;decreasing a resource of the fourth account by the resource transferamount, and sending resource transfer feedback data to the third server,so that the third server increases a resource of a third account forwhich resource transfer is to be performed by the resource transferamount; or if it is determined, based on the resource transfer request,that the third server decreases a resource of a third account for whichresource transfer is to be performed by the resource transfer amount,increasing a resource of the fourth account by the resource transferamount, where the third account is an account on the third server, andthe third account is bound to the fourth account by using theabove-mentioned first or second data processing method.

Some embodiments of the present specification provide a first paymentmethod, applied to a fifth server, including the following: obtaining afirst payment request sent by a terminal device, and determining a fifthaccount, a sixth account from which funds are to be deducted, and apayment amount, where the fifth account is a user login account on thefifth server, and the fifth account is bound to the sixth account byusing the above-mentioned first or second data processing method; andsending a second payment request to a sixth server on which the sixthaccount is located, so that the sixth server decreases the funds in thesixth account by the payment amount.

Some embodiments of the present specification provide a second paymentmethod, applied to a sixth server, including the following: if a paymentrequest sent by a fifth server is obtained, determining a sixth accounton the sixth server from which funds are to be deducted, and determininga payment amount; and decreasing the funds in the sixth account by thepayment amount, and sending payment feedback data to the fifth server,where the sixth account is bound to a fifth account on the fifth serverby using the above-mentioned first or second data processing method, thefifth account is a user login account on the fifth server, and the fifthaccount is used to receive a payment request sent by a terminal device.

Some embodiments of the present specification provide a data processingapparatus, including the following: a preparatory binding module,configured to obtain a user binding request sent by a terminal device,determine a first to-be-bound account on the apparatus, and send userbinding request feedback data to the terminal device so that theterminal device displays candidate binding objects; an initial bindingmodule, configured to obtain binding object selection data sent by theterminal device, determine respective target binding objects based onthe binding object selection data, and determine one or more targetservers among servers corresponding to each of the respective targetbinding objects; and an account binding module, configured to: bind thefirst account to a second account on each target server, and send anaccount binding request to each target server so that the target serverbinds the second account on the target server to the first account,where the second account corresponds to the same user identity data asthe first account.

Some embodiments of the present specification provide a data processingapparatus, including the following: a preparatory binding module,configured to: if an identity authentication request or a bindingconsulting request sent by a first server is obtained, where theidentity authentication request or the binding consulting requestincludes user identity data corresponding to a first account, determinea second account on the apparatus corresponding to the same useridentity data as the first account, where the first account is anaccount on the first server; and send authentication feedback data orconsultation feedback data to the first server, where the authenticationfeedback data or the consultation feedback data includes account data ofthe second account, so that the first server determines one or moretarget servers and sends an account binding request to each targetserver; and an account binding module, configured to: if the accountbinding request sent by the first server is obtained, bind the secondaccount to the first account.

Some embodiments of the present specification provide a resourcetransfer apparatus, including the following: a transfer initiationmodule, configured to obtain a first resource transfer request sent by aterminal device, and determine a third account and a fourth account forwhich resource transfer is to be performed, and a resource transferamount, where the third account is an account on the apparatus, and thethird account is bound to the fourth account by using theabove-mentioned first or second data processing method; and a transfermodule, configured to send a second resource transfer request to afourth server on which the fourth account is located, so that the fourthserver decreases a resource of the fourth account by the resourcetransfer amount; obtain resource transfer feedback data sent by thefourth server, and if it is determined, based on the resource transferfeedback data, that the resource of the fourth account is decreased bythe resource transfer amount, increase a resource of the third accountby the resource transfer amount; or decrease a resource of the thirdaccount by the resource transfer amount, and send a second resourcetransfer request to a fourth server on which the fourth account islocated, so that the fourth server increases a resource of the fourthaccount by the resource transfer amount.

Some embodiments of the present specification provide a resourcetransfer apparatus, including the following: a transfer acceptancemodule, configured to: if a resource transfer request sent by a thirdserver is obtained, determine a fourth account on the apparatus forwhich resource transfer is to be performed, and determine a resourcetransfer amount; and a transfer module, configured to decrease aresource of the fourth account by the resource transfer amount, and sendresource transfer feedback data to the third server, so that the thirdserver increases a resource of a third account for which resourcetransfer is to be performed by the resource transfer amount; or if it isdetermined, based on the resource transfer request, that the thirdserver decreases a resource of a third account for which resourcetransfer is to be performed by the resource transfer amount, increase aresource of the fourth account by the resource transfer amount, wherethe third account is an account on the third server, and the thirdaccount is bound to the fourth account by using the above-mentionedfirst or second data processing method.

Some embodiments of the present specification provide a paymentapparatus, including the following: a payment initiation module,configured to obtain a first payment request sent by a terminal device,and determine a fifth account, a sixth account from which funds are tobe deducted, and a payment amount, where the fifth account is a userlogin account on the apparatus, and the fifth account is bound to thesixth account by using the above-mentioned first or second dataprocessing method; and a payment module, configured to send a secondpayment request to a sixth server on which the sixth account is located,so that the sixth server decreases the funds in the sixth account by thepayment amount.

Some embodiments of the present specification provide a paymentapparatus, including the following: a payment acceptance module,configured to: if a payment request sent by a fifth server is obtained,determine a sixth account on the apparatus from which funds are to bededucted, and determine a payment amount; and a payment module,configured to decrease the funds in the sixth account by the paymentamount, and send payment feedback data to the fifth server, where thesixth account is bound to a fifth account on the fifth server by usingthe above-mentioned first or second data processing method, the fifthaccount is a user login account on the fifth server, and the fifthaccount is used to receive a payment request sent by a terminal device.

Some embodiments of the present specification provide a data processingdevice, including the following: at least one processor; and a memorycommunicatively connected to the at least one processor, where thememory stores an instruction that can be executed by the at least oneprocessor, and the instruction is executed by the at least one processorto enable the at least one processor to perform the above-mentionedfirst or second data processing method.

Some embodiments of the present specification provide a resourcetransfer device, including the following: at least one processor; and amemory communicatively connected to the at least one processor, wherethe memory stores an instruction that can be executed by the at leastone processor, and the instruction is executed by the at least oneprocessor to enable the at least one processor to perform theabove-mentioned first or second resource transfer method.

Some embodiments of the present specification provide a payment device,including the following: at least one processor; and a memorycommunicatively connected to the at least one processor, where thememory stores an instruction that can be executed by the at least oneprocessor, and the instruction is executed by the at least one processorto enable the at least one processor to perform the above-mentionedfirst or second payment method.

Some embodiments of the present specification provide acomputer-readable storage medium, where the computer-readable storagemedium stores a computer-executable instruction, and thecomputer-executable instruction is executed by a processor to implementthe above-mentioned first or second data processing method.

Some embodiments of the present specification provide acomputer-readable storage medium, where the computer-readable storagemedium stores a computer-executable instruction, and thecomputer-executable instruction is executed by a processor to implementthe above-mentioned first or second resource transfer method.

Some embodiments of the present specification provide acomputer-readable storage medium, where the computer-readable storagemedium stores a computer-executable instruction, and thecomputer-executable instruction is executed by a processor to implementthe above-mentioned first or second payment method.

At least one of the above-mentioned technical solutions used in theembodiments of the present specification can achieve the followingbeneficial effects:

One-to-many account binding can be implemented at one single time,thereby improving account binding efficiency, and improving efficiencyof resource transfer and payment between bound accounts.

BRIEF DESCRIPTION OF DRAWINGS

To describe the embodiments of the present specification or thetechnical solutions in the existing technology more clearly, thefollowing briefly describes the accompanying drawings for describing theembodiments of the present specification or the existing technology.Clearly, the accompanying drawings in the following descriptions merelyshow some embodiments of the present specification, and a person ofordinary skill in the art can still derive other drawings from theseaccompanying drawings without creative efforts.

FIG. 1 is a schematic diagram illustrating an execution body of a dataprocessing method, according to a first embodiment of the presentspecification;

FIG. 2 is a schematic flowchart illustrating a data processing method,according to a first embodiment of the present specification;

FIG. 3 is a schematic diagram illustrating a data processing procedure,according to a first embodiment of the present specification;

FIG. 4 is a schematic diagram illustrating a page, according to a firstembodiment of the present specification;

FIG. 5 is a schematic diagram illustrating another page, according to afirst embodiment of the present specification;

FIG. 6 is a schematic diagram illustrating another page, according to afirst embodiment of the present specification;

FIG. 7 is a schematic diagram illustrating another page, according to afirst embodiment of the present specification;

FIG. 8 is a schematic diagram illustrating another page, according to afirst embodiment of the present specification;

FIG. 9 is a schematic diagram illustrating another page, according to afirst embodiment of the present specification;

FIG. 10 is a schematic diagram illustrating another page, according to afirst embodiment of the present specification;

FIG. 11 is a schematic flowchart illustrating a data processing method,according to a second embodiment of the present specification;

FIG. 12 is a schematic flowchart illustrating a resource transfermethod, according to a third embodiment of the present specification;

FIG. 13 is a schematic flowchart illustrating a resource transfermethod, according to a fourth embodiment of the present specification;

FIG. 14 is a schematic flowchart illustrating a payment method,according to a fifth embodiment of the present specification;

FIG. 15 is a schematic flowchart illustrating a payment method,according to a sixth embodiment of the present specification;

FIG. 16 is a schematic structural diagram illustrating a data processingapparatus, according to a seventh embodiment of the presentspecification;

FIG. 17 is a schematic structural diagram illustrating a data processingapparatus, according to an eighth embodiment of the presentspecification;

FIG. 18 is a schematic structural diagram illustrating a resourcetransfer apparatus, according to a ninth embodiment of the presentspecification;

FIG. 19 is a schematic structural diagram illustrating a resourcetransfer apparatus, according to a tenth embodiment of the presentspecification;

FIG. 20 is a schematic structural diagram illustrating a paymentapparatus, according to an eleventh embodiment of the presentspecification; and

FIG. 21 is a schematic structural diagram illustrating a paymentapparatus, according to a twelfth embodiment of the presentspecification.

DESCRIPTION OF EMBODIMENTS

To make a person skilled in the art better understand the technicalsolutions in the present specification, the following clearly and fullydescribes the technical solutions in the embodiments of the presentspecification with reference to the accompanying drawings in theembodiments of the present specification. Clearly, the describedimplementations are merely some but not all of the embodiments of thepresent application. All other embodiments obtained by a person ofordinary skill in the art based on the embodiments of the presentspecification without creative efforts should fall within the protectionscope of the present application.

In existing technologies, people can use a variety of Internet servicesthrough Internet accounts. Some Internet services enable users to binddifferent Internet accounts to satisfy service needs or to improve userexperience.

A first embodiment (hereinafter referred to as “the present embodiment”)of the present specification provides a data processing method, and anexecution body of the present embodiment can be a terminal device(including but not limited to a mobile phone, a computer, a pad, and atelevision), a server, an operating system, a data processing platform,a data processing system, etc., that is, the execution body can bediverse, and the execution body can be set, used, or transformed asneeded. In addition, a third-party application can alternatively beprovided to assist the execution body in executing the presentembodiment. For example, as shown in FIG. 1 , the data processing methodin the present embodiment can be performed by a server, an application(corresponding to the server) can be installed on a terminal device(held by a user), data can be transmitted between the terminal device orthe application and the server, and the terminal device or theapplication can be used to collect, input, or output data, or process apage or information (for the user), thereby assisting the server inperforming the data processing method in the present embodiment.

As shown in FIG. 2 and FIG. 3 , the data processing method provided bythe present embodiment is applied to a first server, and includes thefollowing:

S101: (An execution body) obtains a user binding request sent by aterminal device, determines a first to-be-bound account on the firstserver, and sends user binding request feedback data to the terminaldevice so that the terminal device displays candidate binding objects.

In the present embodiment, the execution body can be the first server.The execution body can obtain a user binding request sent by theterminal device (which can be referred to as a “trigger terminaldevice”), and determine a first to-be-bound account on the first server.

The trigger terminal device can send the user binding request by using aplurality of methods. For example, the above-mentioned correspondingapplication (which can be referred to as a trigger application) can beinstalled on the trigger terminal device. When a user opens acorresponding interface of the trigger application, an account bindingservice is provided for the user through a corresponding option, abutton, etc. on the interface. For example, the interface shown in FIG.4 includes the “I want to bind” option. The user can tap this option toinitiate the account binding service. Because the user operates thetrigger application to initiate the account binding service, and thefirst server is a server corresponding to the trigger application, afterthe user initiates the account binding service, the trigger terminaldevice can generate a user binding request based on the user operation,and send the user binding request to the first server. Correspondingly,the first server obtains the user binding request sent by the triggerterminal device. Specifically, the first server receives the userbinding request sent by the trigger terminal device (receiving a requestis a type of obtaining a request).

The first server can determine the first to-be-bound account on thefirst server based on one or more of method 1.1 or method 1.2 (thepresent embodiment is not limited to the one or more of method 1.1 ormethod 1.2).

1.1. The first account is a login account of the trigger terminal devicewhen the user binding request is obtained.

When the user operates the trigger application, if the user logs in toan account on the first server through the trigger terminal device (thatis, the trigger application on the trigger terminal device), as shown inFIG. 4 , after the user initiates the account binding service, thetrigger terminal device sends the user binding request to the firstserver, and the first server can use the user's login account on thetrigger terminal device (the account on the first server) as the firstto-be-bound account.

1.2. The first account is determined based on the user binding request.

After the user initiates the account binding service, the triggerapplication can display a corresponding input box for the user to inputaccount information (such as a user name or an account number), as shownin FIG. 5 ; because the user operates the trigger application toinitiate the account binding service, the user usually should input theaccount number of the user on the first server; and/or, after the userinitiates the account binding service, the trigger application candisplay an account list of the user (a list of accounts of the user thathave been created on the first server) for the user to select anaccount. For example, FIG. 5 shows a case in which there are three firstserver accounts, and FIG. 5 is only for illustration and does notrepresent actual accounts.

The trigger terminal device can include the account input or selected bythe user in the user binding request and send the user binding requestto the first server, so that the first server can determine the firstaccount based on the user binding request, for example, use the accountincluded in the user binding request as the first to-be-bound account.

After determining the first to-be-bound account, the first server cansend user binding request feedback data to the trigger terminal device,so that the trigger terminal device displays candidate binding objects.The candidate binding object is an object that can be bound, and the“object” here can be a name of an organization, a name of a serviceprovider, etc. All parties of the first server can pre-build relatedInternet protocols with each object, such as a data transfer protocol, adata authentication protocol, etc. The objects that build theabove-mentioned Internet protocols with the service parties of the firstserver can be referred to as candidate binding objects, that is, thetrigger terminal device can display a list of candidate binding objectsfor the user to select. For example, FIG. 6 shows a case in which thereare four candidate binding objects, and FIG. 6 is only for illustrationand does not represent actual object names.

After determining the first to-be-bound account, and before sending theuser binding request feedback data to the trigger terminal device, thefirst server can perform identity authentication or other authenticationon the user identity data corresponding to the first account, and thensend the user binding request feedback data to the trigger terminaldevice after the authentication succeeds.

S103: (The execution body) obtains binding object selection data sent bythe terminal device, determines respective target binding objects basedon the binding object selection data, and determines one or more targetservers among servers corresponding to each of the respective targetbinding objects.

After displaying the candidate binding object, the trigger terminaldevice can determine the object selected by the user based on the useroperation, and send binding object selection data to the first server.The binding object selection data can include the user's selection dataof the candidate binding object. The first server obtains the bindingobject selection data sent by the trigger terminal device, anddetermines the object selected by the user based on the binding objectselection data. The object selected by the user is used as the targetbinding object. That is, the first server determines respective targetbinding objects based on the binding object selection data.

After determining respective target binding objects, the first servercan determine one or more target servers among the servers correspondingto each of the respective target binding objects, and send an accountbinding request to each target server. As described above, the “object”can be a name of an organization, a name of a service provider, etc. Aserver corresponding to any object can be a subordinate server of anorganization represented by the object or a server used to provide aservice represented by the object.

Specifically, the determining one or more target servers among theservers corresponding to each of the respective target binding objectscan be implemented using the following method:

S1031: Before sending an account binding request to each target server,the first server sends an identity authentication request or a bindingconsulting request to the server corresponding to respective targetbinding objects, where the identity authentication request or thebinding consulting request includes the user identity data correspondingto the first account, so that any server corresponding to respectivetarget binding objects determines a second account on the servercorresponding to the same user identity data as the first account.

Specifically, after determining respective target binding objects, thefirst server can send an identity authentication request or a bindingconsulting request to the server corresponding to respective targetbinding objects, where the identity authentication request or thebinding consulting request includes the user identity data correspondingto the first account (that is, the user identity data used to registerthe first account, including but not limited to the user's identity cardnumber or other identity numbers), so that any server corresponding torespective target binding objects determines the second account on theserver after receiving the identity authentication request or thebinding request. The second account corresponds to the same useridentity data as the first account.

For example, the target binding objects include object A, object B, andobject C. In this case, the first server can send an identityauthentication request or a binding consulting request to a servercorresponding to object A, a server corresponding to object B, and aserver corresponding to object C, so that the server corresponding toobject A determines a second account on the server corresponding to thesame user identity data as the first account, the server correspondingto object B determines a second account on the server corresponding tothe same user identity data as the first account, and the servercorresponding to object C determines a second account on the servercorresponding to the same user identity data as the first account.Generally, different target binding objects correspond to differentservers. If there are a plurality of target binding objects, there canbe a plurality of servers corresponding to each of the respective targetbinding objects, and there can be a plurality of determined secondaccounts.

Any server corresponding to the target binding object can sendauthentication feedback data or consultation feedback data to the firstserver.

S1033: After sending the identity authentication request or the bindingconsulting request to any server corresponding to respective targetbinding objects, the first server obtains authentication feedback dataor consultation feedback data sent by any server corresponding torespective target binding objects, and determines the second account onthe server based on the authentication feedback data or the consultationfeedback data sent by the server.

Specifically, after sending the identity authentication request or thebinding consulting request to any server corresponding to respectivetarget binding objects, the first server can obtain the authenticationfeedback data (corresponding to the identity authentication request) orthe consultation feedback data (corresponding to the binding consultingrequest) sent by any server corresponding to respective target bindingobjects. The authentication feedback data or the consultation feedbackdata sent by any server corresponding to respective target bindingobjects can include account information of the second account determinedby the server, and the first server can determine the second account onthe server based on the authentication feedback data or the consultationfeedback data sent by the server.

S1035: After determining the second account on any server correspondingto respective target binding objects based on the authenticationfeedback data or the consultation feedback data sent by the server, thefirst server sends candidate account data to the trigger terminaldevice, where the candidate account data is used to enable the terminaldevice to display the second account that is determined by the servercorresponding to respective target binding objects.

Specifically, after determining the second account on each servercorresponding to respective target binding objects, the first server cansend candidate account data to the trigger terminal device. Thecandidate account data can include the account information of the secondaccount on each server corresponding to respective target bindingobjects, so that the trigger terminal device displays the second accounton each server corresponding to respective target binding objects. Thesecond account can be used as a candidate binding account for the firstaccount, that is, the trigger terminal device can display a list ofsecond accounts for the user to select. For example, as shown in FIG. 7, assume that the user selects candidate binding objects 1 to 3, theserver of object 1 has three second accounts, and objects 2 and 3 eachhave one second account. FIG. 7 is only for illustration and does notrepresent actual object names.

The following further describes two possible cases.

Case 1: The above-mentioned second account does not exist on one or moreservers corresponding to each of the respective target binding objects.

The above-mentioned second account may not exist on the servercorresponding to some target binding objects. Assume that server S1 isthe server corresponding to target binding object A (only used as anexample and not specific), and server S1 does not have theabove-mentioned second account. In this case, after obtaining theauthentication feedback data or the consultation feedback data sent byserver S1, the first server can determine that the above-mentionedsecond account does not exist on server S1 based on the authenticationfeedback data or the consultation feedback data sent by server S1. Inthis case, the candidate account data is further used to enable thetrigger terminal device to display first prompt information, and thefirst prompt information is used to prompt that there is no account thatcan be bound to the target binding object corresponding to the server onwhich the second account does not exist. For example, the servercorresponding to object 3 does not have a second account, as shown inFIG. 8 . Following the above-mentioned example, the first promptinformation is used to prompt that there is no account that can be boundto target binding object A. If there are a plurality of target bindingobjects for which there is no account that can be bound, respectivetarget binding objects for which there is no account that can be boundcan have the above-mentioned first prompt information.

Following the above-mentioned example, if the second account does notexist on a server corresponding to the target binding object, thecandidate account data is further used to enable the trigger terminaldevice to display second prompt information, and the second promptinformation is used to prompt a user to create an account for “thetarget binding object corresponding to the server on which the secondaccount does not exist”. For example, the server corresponding to object3 does not have a second account, and the second prompt informationprompts to create the account of object 3, as shown in FIG. 8 .Following the above-mentioned example, if the above-mentioned secondaccount does not exist on server S1, the second prompt information isused to prompt the user to create the account of target binding objectA, and the account of target binding object A is the account on serverS1. If there are a plurality of target binding objects for which thereis no account that can be bound, respective target binding objects forwhich there is no account that can be bound can have the above-mentionedsecond prompt information. In addition, the second prompt informationcan be in a form of an option or a button, and the user can create anaccount by tapping the second prompt information, as shown in FIG. 8 ,for example.

As described above, if the trigger terminal device displays the secondprompt information, the user may need to create an account for “thetarget binding object corresponding to the server on which the secondaccount does not exist”. For example, the user taps the second promptinformation. In this case, the trigger terminal device can obtain theuser's account creation request, and send the user creation request tothe first server. As described above, if there are a plurality of targetbinding objects for which there is no account that can be bound,respective target binding objects for which there is no account that canbe bound can have the above-mentioned second prompt information. In thiscase, the trigger terminal device can determine a specific targetbinding object, where second prompt information corresponding to thetarget binding object has been tapped by the user. In this way, thetrigger terminal device can determine a specific target binding objectfor which the user needs to create an account, and include (object data)of the target binding object for which the user wants to create anaccount into the user creation request.

Correspondingly, after obtaining the user creation request sent by thetrigger terminal device, the first server can determine one or morespecific target binding objects for which the user wants to create anaccount, use servers corresponding to each of the respective targetbinding objects for which the user wants to create an account as accountcreation servers, that is, the first server determines one or moreaccount creation servers based on the account creation request.

The first server sends an account creation request to each accountcreation server, so that each account creation server creates a secondaccount, and the created second account should correspond to the sameuser identity data as the first account. Because the account creationserver is the server corresponding to the target binding object, theaccount creation server has previously obtained the identityauthentication request or the binding consulting request that is sent bythe first server and that includes the user identity data correspondingto the first account. Therefore, the account creation request caninclude or does not have to include the user identity data correspondingto the first account.

Any account creation server can send creation feedback data to the firstserver, and the creation feedback data can include account data of thecreated second account.

After sending an account creation request to each account creationserver, the first server can obtain creation feedback data sent by anyaccount creation server, and determine the second account to be createdby the account creation server based on the creation feedback data sentby the account creation server.

After obtaining the creation feedback data, the first server can sendsupplemental candidate account data to the trigger terminal device,where the supplemental candidate account data is used to enable theterminal device to display the second account created by each accountcreation server. Because a server corresponding to some target bindingobjects has a second account before the first server sends the identityauthentication request or the binding consulting request, after thefirst server sends the supplemental candidate account data to thetrigger terminal device, the second account created by each accountcreation server can be displayed together with “the server correspondingto the target binding object has the second account before the firstserver sends the identity authentication request or the bindingconsulting request”. For example, the account of the servercorresponding to object 3 is created, as shown in FIG. 9 .

Case 2: There are a plurality of second accounts on one or more serverscorresponding to each of the respective target binding objects.

For any target binding object, if the server corresponding to any targetbinding object determines a plurality of second accounts after obtainingthe identity authentication request or the binding consulting requestsent by the first server, the above-mentioned candidate account data isfurther used to enable the trigger terminal device to display theplurality of second accounts of the server corresponding to the targetbinding object, for example, as shown in any one of FIG. 7 to FIG. 9 .

Assume that server S2 is a server corresponding to target binding objectB (only used as an example and not specific), and server S2 determines aplurality of second accounts after receiving the identity authenticationrequest or the binding consulting request sent by the first server. Inthis case, server S2 can determine one or more recommended secondaccounts (which can be referred to as “recommended accounts”; arecommended account is a second account recommended to be bound) amongthe plurality of second accounts on server S2, and include account dataof the recommended accounts into the authentication feedback data or theconsultation feedback data sent by server S2 to the first server. ServerS2 can determine the recommended accounts based on historical accountoperation data of the plurality of second accounts on server S2.

The first server receives the authentication feedback data or theconsultation feedback data sent by server S2, and determines therecommended account on server S2 based on the authentication feedbackdata or the consultation feedback data sent by server S2. In this case,the above-mentioned candidate account data is further used to enable thetrigger terminal device to display the first recommendation information,and the first recommendation information is used to prompt therecommended account. For example, account 1 on the server correspondingto object 1 is a recommended account, as shown in any one of FIG. 7 toFIG. 9 . For any target binding object, if the server corresponding toany target binding object has a plurality of second accounts, the targetbinding object can have the above-mentioned first recommendationinformation.

In addition, after determining the second account on any servercorresponding to respective target binding objects based on theauthentication feedback data or the consultation feedback data sent bythe server, the first server can further determine the second accountrecommended to be bound among all the second accounts of the servercorresponding to respective target binding objects. The above-mentionedcandidate account data is further used to enable the trigger terminaldevice to display the second recommendation information, and the secondrecommendation information is used to prompt the recommendation of the“determining the second account recommended to be bound among all thesecond accounts”.

Specifically, the first server can determine the second accountrecommended to be bound among the second accounts of the servercorresponding to respective target binding objects based on thehistorical interaction data between the first server and the servercorresponding to respective target binding objects, that is,“determining the second account recommended to be bound among all thesecond accounts”.

S1037: The determining one or more target servers among serverscorresponding to each of the respective target binding objects includesthe following: obtaining binding account selection data sent by theterminal device, determining one or more selected second accounts basedon the binding account selection data, and using a server on which theone or more selected second accounts are located as the target server.

Specifically, for any target binding object, the second account on theserver corresponding to any target binding object is also the secondaccount of the target binding object. After the candidate account datais used to enable the trigger terminal device to display the secondaccount of respective target binding objects, the user can select thesecond to-be-bound account, so that the trigger terminal device canobtain the user's operation on the second account, and generate bindingaccount selection data and send the binding account selection data tothe first server. The binding account selection data can include thesecond account selected by the user.

The first server obtains the binding account selection data sent by thetrigger terminal device, determines one or more second accounts (whichcan be referred to as selected second accounts) selected (by the user)based on the binding account selection data, and uses the server onwhich each selected second account is located as the target server. Itcan be understood that if the selected second accounts come from aplurality of servers, there are a plurality of target servers.

In the present embodiment, the target server can alternatively bedetermined in other ways. For example, after the user selects the targetbinding object, the server corresponding to the target binding object isused as the target server.

Generally, the user selects the target binding object, indicating thatthe user wants to bind the first account to the second account ofrespective target binding objects. If there is a second account forrespective target binding objects, the user selects at least one secondaccount for respective target binding objects, so that the target serveris the server corresponding to the target binding object.

S105: Bind the first account to a second account on each target server,and send an account binding request to each target server so that thetarget server binds the second account on the target server to the firstaccount, where the second account corresponds to the same user identitydata as the first account.

After determining one or more target servers, the first account can bebound to a second account on each target server, that is, the firstserver binds the first account to the second account on each targetserver, and sends an account binding request to each target server sothat the target server binds the second account on the target server tothe first account. Specifically, the first account can be bound to eachselected second account based on one or more of method 2.1 or method 2.2(the present embodiment is not limited to the one or more of method 2.1or method 2.2).

2.1. The target server performs binding first, and then the first serverperforms binding.

The first server can send the account binding request to each targetserver so that the target server binds the second account on the targetserver to the first account; the first server can obtain account bindingrequest feedback data sent by any target server, and if it isdetermined, based on the account binding request feedback data, that thetarget server has bound the second account on the target server to thefirst account, bind the first account to the second account on thetarget server.

For example, for any target server S3, the first server sends an accountbinding request to target server S3, so that target server S3 binds thesecond account on target server S3 to the first account, that is, thetarget server first binds the second account on target server S3 to thefirst account.

Any target server can send account binding request feedback data to thefirst server, and the first server obtains the (first) account bindingrequest feedback data sent by any target server. If it is determined,based on the account binding request feedback data, that the targetserver has bound the second account on the target server to the firstaccount, the first server binds the first account to the second accounton the target server, that is, the first server then binds the firstaccount to the second account.

Following the above-mentioned example, the first server obtains theaccount binding request feedback data sent by target server S3. If it isdetermined, based on the account binding request feedback data sent bytarget server S3, that target server S3 has bound the second account ontarget server S3 to the first account, the first server binds the firstaccount to the second account on target server S3.

2.2. The first server performs binding first, and then the target serverperforms binding.

After binding the first account to the second account on any targetserver, the first server sends the account binding request to the targetserver so that the target server binds the second account on the targetserver to the first account.

The first server can bind the first account to the second account oneach target server, and then make each target server bind the secondaccount on the target server to the first account. For example, for anytarget server S4, the first server binds the first account to the secondaccount on target server S4, that is, the first server first binds thefirst account to the second account; and then the first server sends anaccount binding request to target server S4, so that target server S4binds the second account on target server S4 to the first account, thatis, the target server then binds the second account to the firstaccount.

In method 2.2, after any target server binds the second account on thetarget server to the first account, the target server can send (second)account binding request feedback data to the first server, and the firstserver determines, based on the account binding request feedback data,whether the target server has bound the second account on the targetserver to the first account.

In particular, the account binding request can include user identitydata corresponding to the first account.

In method 2.1 or 2.2, for any target server, if there are a plurality ofsecond accounts on any target server, after the target server obtainsthe account binding request sent by the first server (regardless of theaccount binding request in method 2.1 or 2.2, hereinafter the same), thetarget server can bind all the second accounts on the target server tothe first account, or the target server can bind one of the secondaccounts on the target server to the first account.

In method 2.1 or 2.2, for any target server, before any target serverbinds the second account on the target server to the first account, thetarget server can perform identity authentication or otherauthentication on the user identity data corresponding to the firstaccount, and the user identity data corresponding to the second account,and then bind the second account on the target server to the firstaccount after the authentication succeeds.

In the present embodiment, the sending an account binding request toeach target server so that the target server binds the second account onthe target server to the first account includes the following: sendingan account binding request to each target server so that the targetserver binds one second account on the target server to the firstaccount.

For example, for any target sever S5, if there are a plurality of secondaccounts on any target server S5, the account binding request sent bythe first server enables target server S5 to bind one of the secondaccounts on target server S5 to the first account.

Specifically, in the present embodiment, for any target server, if thereare a plurality of second accounts on any target server, and the userselects one second account of the target server in S1037, the accountbinding request sent by the first server to the target server caninclude the second account selected by the user on the target server, sothat the target server binds the second account selected by the user tothe first account.

The first server binds the first account to the second account, whichcan specifically mean that the first server itself generates and storesa binding relationship between the first account and the second account.The target server binds the second account to the first account, whichcan specifically mean that the target server itself generates and storesa binding relationship between the second account and the first account.An account binding protocol or a consensus protocol can be pre-builtbetween the first server and the server corresponding to each candidatebinding object, so that the first server and the target server cangenerate and store the binding relationship between the first accountand the second account.

In addition, the first server can send user feedback data to the triggerterminal device, so that the trigger terminal device displays an accountbinding result, that is, an account binding result of the first accountand the second account, as shown in FIG. 10 , for example.

In particular, either the first account or the second account can be aresource storage account or a resource transfer account.

It is worthwhile to note that, when the first server sends any requestor any data to any server corresponding to respective target bindingobjects, the first server may not directly send the request or the datato any server corresponding to respective target binding objects, andinstead, the first server sends the request or the data that needs to besent to an intermediate server, and the intermediate server sends therequest or the data that needs to be sent to any server corresponding torespective target binding objects. For example, server S6 is any servercorresponding to the target binding object. When the first server sendsany request or any data to server S6, the first server may not directlysend the request or the data to server S6, and instead, the first serversends the request or the data that needs to be sent to an intermediateserver, and the intermediate server sends the request or the data thatneeds to be sent to server S6.

When any server corresponding to respective target binding objects sendsany request or any data to the first server, any server corresponding torespective target binding objects may not directly send the request orthe data to the first server, and instead, any server corresponding torespective target binding objects sends the request or the data thatneeds to be sent to an intermediate server, and the intermediate serversends the request or the data that needs to be sent to the first server.Following the above-mentioned example, server S6 is any servercorresponding to the target binding object. When server S6 sends anyrequest or any data to the first server, server S6 may not directly sendthe request or the data to the first server, and instead, server S6sends the request or the data that needs to be sent to an intermediateserver, and the intermediate server sends the request or the data thatneeds to be sent to the first server.

Regardless of whether the intermediate server receives the request andthe data from the first server or any server corresponding to respectivetarget binding objects, the intermediate server can perform identityauthentication on the request or the data, and then send the request andthe data to the first server or any server corresponding to respectivetarget binding objects.

It is worthwhile to note that in the present embodiment, the triggerterminal device can be changed. For example, the user logs in to thefirst account on terminal device and initiates the account bindingservice, and then logs in to the first account on terminal device b toselect a second account. In this case, the trigger terminal device ischanged from terminal device a to terminal device b.

In the present embodiment, the candidate binding object can be diverse,and the user is given the right to choose; the first account representsone of the accounts that the user wants to bind; and the target bindingobject represents the object that the user wants to bind.

The first server sends the identity authentication request or thebinding consulting request to the server corresponding to respectivetarget binding objects, and obtains the authentication feedback data orthe consultation feedback data sent by the server corresponding torespective target binding objects, thereby implementing authentication,matching or consensus of the user identity data corresponding to thefirst account between the first server and the server corresponding torespective target binding objects.

The account creation process enables the user to create and bindaccounts at one single time for an object that the user wants to bindand that does not have an account.

By selecting a second account, the user can determine the second accountthat the user wants to bind, that is, the other one of the accounts thatthe user wants to bind. In addition, the user can select a plurality ofsecond accounts, so as to complete the binding between the first accountand the second account.

In the present embodiment, the user first selects the target bindingobject, and further determines the server corresponding to respectivetarget binding objects among the servers corresponding to the candidateobjects, and makes the server corresponding to respective target bindingobjects determine the second account on the server. Then, the userselects the second account, and further determines the target serveramong the servers corresponding to each of the respective target bindingobjects, thereby implementing the binding between the first account andthe second account on each target server.

According to the present embodiment, one-to-many account binding can beimplemented at one single time, that is, one first account is bound to aplurality of second accounts, thereby improving the efficiency ofaccount binding. The user does not need to input personal identity dataduring binding, and the first server can automatically obtain the useridentity data corresponding to the first account, further improving theefficiency of account binding and improving the security of accountbinding.

In the existing technology, to perform electronic payment and improveexperience of the electronic payment, the user can bind a third-partypayment account of the user to an account of a financial institution(including but not limited to a bank) to create an electronic paymentservice such as quick payment. To implement quick payment, the bankaccount of the user needs to be bound to an account of a third-partypayment institution in advance under the framework of a tripartiteagreement (among the user, the bank, and the payment institution).

As the quantity of third-party payment institutions increases, the usermay need to bind the financial institution account (a bank account isused as an example in the following description) of the user to accountsof a plurality of third-party payment institutions. However, in theexisting technology, the user has to initiate the binding of the bankaccount through a third-party payment institution, and each third-partypayment institution can only bind its own account to the bank account.In addition, processes of binding various third-party paymentinstitutions to the bank account are different. Consequently, the userneeds to input the binding elements (including but not limited to aname, identity information, a bank card number, and a mobile phonenumber) in each binding process. The user is likely to fill in wronginformation, resulting in a complicated binding process and low bindingefficiency.

In the present embodiment, the bank server can be used as the firstserver, the bank account can be used as the first account, eachthird-party payment institution can be used as the candidate bindingobject, the server of each third-party payment institution can be usedas the target server, and the account of the third-party paymentinstitution can be used as the second account, so that one bank accountcan be bound to the accounts of a plurality of third-party institutionsat one single time, effectively improving the efficiency of accountbinding. In the present embodiment, the account binding can be initiatedfrom the bank, without relying on various third-party paymentinstitutions. During the account binding, the user does not need toinput personal information, and the bank can automatically obtain thefirst account and the user identity information corresponding to thefirst account, further improving the efficiency of account binding andthe security of account binding.

It is worthwhile to note that in the process of binding the account ofthe financial institution to the account of the third-party paymentinstitution, the above-mentioned intermediate server can be a server ofNETPAY or UNIONPAY.

The first embodiment of the present specification is mainly describedfrom the perspective of the first server, and the second embodiment ofthe present specification is mainly described from the perspective ofthe second server (further, from the perspective of the target server).

A second embodiment (hereinafter referred to as “the presentembodiment”) of the present specification provides a data processingmethod, and an execution body of the present embodiment can be aterminal device (including but not limited to a mobile phone, acomputer, a pad, and a television), a server, an operating system, adata processing platform, a data processing system, etc., that is, theexecution body can be diverse, and the execution body can be set, used,or transformed as needed. In addition, a third-party application canalternatively be provided to assist the execution body in executing thepresent embodiment. For example, as shown in FIG. 1 , the dataprocessing method in the present embodiment can be performed by aserver, an application (corresponding to the server) can be installed ona terminal device (held by a user), data can be transmitted between theterminal device or the application and the server, and the terminaldevice or the application can be used to collect, input, or output data,or process a page or information (for the user), thereby assisting theserver in performing the data processing method in the presentembodiment.

As shown in FIG. 11 , the data processing method provided in the presentembodiment is applied to the second server (that is, the execution bodyis the second server), and includes the following:

S202: If an identity authentication request or a binding consultingrequest sent by a first server is obtained, where the identityauthentication request or the binding consulting request includes useridentity data corresponding to a first account, determine a secondaccount on the second server corresponding to the same user identitydata as the first account, where the first account is an account on thefirst server.

The second server in the present embodiment obtains the identityauthentication request or the binding consulting request sent by thefirst server. This means that the second server in the presentembodiment is a server corresponding to the target binding object in thefirst embodiment, that is, a server corresponding to the candidatebinding object.

S204: Send authentication feedback data or consultation feedback data tothe first server, where the authentication feedback data or theconsultation feedback data includes account data of the second account,so that the first server determines one or more target servers and sendsan account binding request to each target server.

In the present embodiment, the identity authentication request or thebinding consulting request sent by the first server is obtained. Ifthere is no account on the second server corresponding to the same useridentity data as the first account, the authentication feedback data orthe consultation feedback data is used to enable the first server todetermine that there is no account on the second server corresponding tothe same user identity data as the first account.

In the present embodiment, if an account creation request sent by thefirst server is received, the second account corresponding to the sameuser identity data as the first account is created based on the accountcreation request; and creation feedback data is sent to the firstserver, where the creation feedback data includes the account data ofthe second account that is created based on the account creationrequest.

In the present embodiment, if there are a plurality of second accounts,the authentication feedback data or the consultation feedback datafurther includes account data of a recommended account, and therecommended account is one or more second accounts.

In the present embodiment, the recommended account is determined basedon historical account operation data of the plurality of secondaccounts.

S206: If the account binding request sent by the first server isobtained, bind the second account to the first account.

The account binding request here can be the account binding request inmethod 2.1 or 2.2. This means that the second server in the presentembodiment has become a particular target server in the firstembodiment.

In the present embodiment, if there are a plurality of second accounts,the binding the second account to the first account includes thefollowing: determining a second to-be-bound account among the pluralityof second accounts based on the account binding request, and binding thesecond to-be-bound account to the first account.

In the present embodiment, if there are a plurality of second accounts,the binding the second account to the first account includes thefollowing: determining a second to-be-bound account among the pluralityof second accounts, and binding the second to-be-bound account to thefirst account.

After binding the second account on the second server to the firstaccount, the second server can send account binding request feedbackdata to the first server.

The account binding request feedback data here can be the accountbinding request feedback data in method 2.1, or the account bindingrequest feedback data in method 2.2.

Referring to the first embodiment, in the present embodiment, if thesecond server needs to send any request or any data to the first server,the second server can send any request or any data to an intermediateserver, and the intermediate server sends any request or any data to thefirst server.

For the content not described in detail in the present embodiment,references can be made to the first embodiment.

According to the present embodiment, one-to-many account binding can beimplemented at one single time, that is, one first account is bound to aplurality of second accounts, thereby improving the efficiency ofaccount binding. The user does not need to input personal identity dataduring binding, and the first server can automatically obtain the useridentity data corresponding to the first account, further improving theefficiency of account binding and improving the security of accountbinding.

The present embodiment, such as the first embodiment, can be applied tothe binding between an account of a financial institution and an accountof a third-party payment institution.

As shown in the first embodiment, both the first account and the secondaccount can be resource storage accounts or resource transfer accounts.After the first account is bound to the second account through the firstor second embodiment, a resource can be transferred between the firstaccount and each second account bound to the first account.

A third embodiment (hereinafter referred to as “the present embodiment”)of the present specification provides a resource transfer method, and anexecution body of the present embodiment can be a terminal device(including but not limited to a mobile phone, a computer, a pad, and atelevision), a server, an operating system, a resource transferplatform, a resource transfer system, etc., that is, the execution bodycan be diverse, and the execution body can be set, used, or transformedas needed. In addition, a third-party application can alternatively beprovided to assist the execution body in executing the presentembodiment. For example, as shown in FIG. 1 , the resource transfermethod in the present embodiment can be performed by a server, anapplication (corresponding to the server) can be installed on a terminaldevice (held by a user), data can be transmitted between the terminaldevice or the application and the server, and the terminal device or theapplication can be used to collect, input, or output data, or process apage or information (for the user), thereby assisting the server inperforming the resource transfer method in the present embodiment.

As shown in FIG. 12 , the resource transfer method provided in thepresent embodiment is applied to a third server (that is, the executionbody is the third server), and includes the following:

S301: Obtain a first resource transfer request sent by a terminaldevice, and determine a third account and a fourth account for whichresource transfer is to be performed, and a resource transfer amount,where the third account is an account on the third server, and the thirdaccount is bound to the fourth account by using the method described inthe first or second embodiment.

The third server in the present embodiment is equivalent to the firstserver in the first embodiment or the second server (or the targetserver) in the second embodiment.

The third server can obtain the first resource transfer request sent bythe terminal device (which can be referred to as a “second triggerterminal device”, the trigger terminal device in the first embodiment isa first trigger terminal device, and the first trigger terminal deviceand the second trigger terminal device can be the same or different).

Referring to the first embodiment, the user can initiate the resourcetransfer service through the application corresponding to the thirdserver, and then the second trigger terminal device sends the firstresource transfer request to the third server.

The third account for which resource transfer is to be performed is anaccount on the third server, and the method for determining the thirdaccount is determined according to the method for determining the firstaccount, for example, by user input or determined based on the loginaccount of the second trigger terminal device. Both the first accountand any second account bound to the first account can be used asresource outbound accounts or resource inbound accounts. Therefore, thethird account can be equivalent to the first account or the secondaccount.

The fourth account for which resource transfer is to be performed can bedetermined by the user and included in the first resource transferrequest. Therefore, the third server can determine the fourth accountbased on the first resource transfer request. Similarly, both the firstaccount and any second account bound to the first account can be used asresource outbound accounts or resource inbound accounts. Therefore, thethird account can be equivalent to the first account or the secondaccount.

The resource transfer amount can be included in the first resourcetransfer request, and therefore the third server can determine theresource transfer amount based on the first resource transfer request.

The third account is bound to the fourth account by using the methoddescribed in the first or second embodiment. If (the third serverdetermines that) the third account has not been bound to the fourthaccount when the first resource transfer request is obtained, like thefirst server in the first embodiment, the third server can use the dataprocessing method in the first embodiment to bind the third account tothe fourth account.

S303: Send a second resource transfer request to a fourth server onwhich the fourth account is located, so that the fourth server decreasesa resource of the fourth account by the resource transfer amount; obtainresource transfer feedback data sent by the fourth server, and if it isdetermined, based on the resource transfer feedback data, that theresource of the fourth account is decreased by the resource transferamount, increase a resource of the third account by the resourcetransfer amount; or decrease a resource of the third account by theresource transfer amount, and send a second resource transfer request toa fourth server on which the fourth account is located, so that thefourth server increases a resource of the fourth account by the resourcetransfer amount.

The second resource transfer request can include account data of thefourth account and the resource transfer amount, so that after thefourth server on which the fourth account is located obtains the secondresource transfer request, the fourth server determines a fourth accounton the fourth server for which resource transfer is to be performed, anddetermines a resource transfer amount.

If the first resource transfer request is to transfer a resource fromthe fourth account to the third account, that is, the third server is aresource inbound server, the third server sends a second resourcetransfer request to a fourth server on which the fourth account islocated, so that the fourth server decreases a resource of the fourthaccount by the resource transfer amount; the third server obtainsresource transfer feedback data sent by the fourth server, and if it isdetermined, based on the resource transfer feedback data, that theresource of the fourth account is decreased by the resource transferamount, increases a resource of the third account by the resourcetransfer amount.

If the first resource transfer request is to transfer a resource fromthe third account to the fourth account, that is, the third server is aresource outbound server, the third server decreases a resource of thethird account by the resource transfer amount, and sends a secondresource transfer request to a fourth server on which the fourth accountis located, so that the fourth server increases a resource of the fourthaccount by the resource transfer amount.

The third server can send user feedback data to the second triggerterminal device, so that the second trigger terminal device displays theresource transfer result.

Referring to the first or second embodiment, the data transmissionbetween the third server and the fourth server can be performed throughan intermediate server.

In the present embodiment, the third account is bound to the fourthaccount by using the method in the first or second embodiment. This canimplement one-to-many account binding at one single time and improve theefficiency of account binding. The resource transfer through the boundaccount further improves the efficiency of resource transfer.

A fourth embodiment (hereinafter referred to as “the presentembodiment”) of the present specification provides a resource transfermethod, and an execution body of the present embodiment can be aterminal device (including but not limited to a mobile phone, acomputer, a pad, and a television), a server, an operating system, aresource transfer platform, a resource transfer system, etc., that is,the execution body can be diverse, and the execution body can be set,used, or transformed as needed. In addition, a third-party applicationcan alternatively be provided to assist the execution body in executingthe present embodiment. For example, as shown in FIG. 1 , the resourcetransfer method in the present embodiment can be performed by a server,an application (corresponding to the server) can be installed on aterminal device (held by a user), data can be transmitted between theterminal device or the application and the server, and the terminaldevice or the application can be used to collect, input, or output data,or process a page or information (for the user), thereby assisting theserver in performing the resource transfer method in the presentembodiment.

As shown in FIG. 13 , the resource transfer method provided in thepresent embodiment is applied to a fourth server (that is, the executionbody is the fourth server), and includes the following:

S402: If a resource transfer request sent by a third server is obtained,determine a fourth account on the fourth server for which resourcetransfer is to be performed, and determine a resource transfer amount.

The third server in the present embodiment is equivalent to the firstserver in the first embodiment or the second server (or the targetserver) in the second embodiment, and the resource transfer request inthe present embodiment is the second resource transfer request in thethird embodiment.

S404: Decrease a resource of the fourth account by the resource transferamount, and send resource transfer feedback data to the third server, sothat the third server increases a resource of a third account for whichresource transfer is to be performed by the resource transfer amount; orif it is determined, based on the resource transfer request, that thethird server decreases a resource of a third account for which resourcetransfer is to be performed by the resource transfer amount, increase aresource of the fourth account by the resource transfer amount, wherethe third account is an account on the third server, and the thirdaccount is bound to the fourth account by using the method described inthe first or second embodiment.

For the content not described in detail in the present embodiment,references can be made to the third embodiment.

In the present embodiment, the third account is bound to the fourthaccount by using the method in the first or second embodiment. This canimplement one-to-many account binding at one single time and improve theefficiency of account binding. The resource transfer through the boundaccount further improves the efficiency of resource transfer.

The resource in the third or fourth embodiment includes a virtualresource, and the virtual resource includes funds. Therefore, theresource transfer in the third or fourth embodiment can be fundstransfer, such as top-up from the third account to the fourth account ortop-up from the fourth account to the third account, so the third orfourth embodiment can alternatively include a top-up method.

Payment can be used as a type of funds transfer, so the third or fourthembodiment can alternatively include a payment method.

A fifth embodiment (hereinafter referred to as “the present embodiment”)of the present specification provides a payment method, and an executionbody of the present embodiment can be a terminal device (including butnot limited to a mobile phone, a computer, a pad, and a television), aserver, an operating system, a payment platform, a payment system, etc.,that is, the execution body can be diverse, and the execution body canbe set, used, or transformed as needed. In addition, a third-partyapplication can alternatively be provided to assist the execution bodyin executing the present embodiment. For example, as shown in FIG. 1 ,the payment method in the present embodiment can be performed by aserver, an application (corresponding to the server) can be installed ona terminal device (held by a user), data can be transmitted between theterminal device or the application and the server, and the terminaldevice or the application can be used to collect, input, or output data,or process a page or information (for the user), thereby assisting theserver in performing the payment method in the present embodiment.

As shown in FIG. 14 , the payment method provided in the presentembodiment is applied to a fifth server (that is, the execution body isthe fifth server), and includes the following:

S501: Obtain a first payment request sent by a terminal device, anddetermine a fifth account, a sixth account from which funds are to bededucted, and a payment amount, where the fifth account is a user loginaccount on the fifth server, and the fifth account is bound to the sixthaccount by using the method described in the first or second embodiment.

The fifth server in the present embodiment is equivalent to any one ofthe first to fourth servers, or can be the target server in the secondembodiment.

The fifth server can obtain the first payment request sent by theterminal device (which can be referred to as a “third trigger terminaldevice”; the first, second, and third trigger terminal devices can bethe same or different).

Referring to the first embodiment, the user can initiate the resourcetransfer service through the application corresponding to the fifthserver, and then the third trigger terminal device sends the firstpayment request to the fifth server.

The fifth account is an account on the fifth server, and the method fordetermining the fifth account is determined according to the method fordetermining the first account, for example, by user input or determinedbased on the login account of the third trigger terminal device.Although the fifth server obtains the first payment request, the fifthaccount may not be a funds deduction account. For example, in a quickpayment scenario, the server of the third-party payment institutionobtains the first payment request sent by the user terminal device, butthe funds deduction account can be a financial institution account boundto the account of the third-party payment institution.

The sixth account from which funds are to be deducted can be determinedby the user and be included in the first payment request, so the fifthserver can determine the sixth account based on the first paymentrequest.

The payment amount can be included in the first payment request, so thefifth server can determine the payment amount based on the first paymentrequest.

The fifth account is bound to the sixth account by using the methoddescribed in the first or second embodiment. If (the fifth serverdetermines that) the fifth account has not been bound to the sixthaccount when the first payment request is obtained, like the firstserver in the first embodiment, the fifth server can use the dataprocessing method in the first embodiment to bind the fifth account tothe sixth account.

S503: Send a second payment request to a sixth server on which the sixthaccount is located, so that the sixth server decreases the funds in thesixth account by the payment amount.

The second payment request can include account data of the sixth accountand the payment amount, so that after the sixth server on which thesixth account is located obtains the second payment request, the sixthserver determines the sixth account for which payment is to be performedon the sixth server, and determines the payment amount.

After decreasing the funds in the sixth account by the payment amount,the sixth server can send payment feedback data to the fifth server. Ifthe fifth server determines, based on the payment feedback data sent bythe sixth server, that the payment amount has been deducted from thesixth account, the fifth server can send the user feedback data to thethird trigger terminal device so that the third trigger terminal devicedisplays the payment result.

If the fifth server is the funds receiving server corresponding to thepayment, the fifth server can increase the funds in the funds receivingaccount on the fifth server by the payment amount after determining,based on the payment feedback data sent by the sixth server, that thepayment amount has been deducted from the sixth account.

If the fifth server is not the funds receiving server corresponding tothe payment, the fifth server can send a funds receiving instruction tothe funds receiving server after the fifth server determines, based onthe payment feedback data sent by the sixth server, that the paymentamount has been deducted from the sixth account, so that the fundsreceiving server adds the payment amount to the funds receiving accounton the funds receiving server.

The fifth server can be a server of a third-party payment institution,the sixth server can be a server of a financial institution, the fifthaccount can be a third-party payment institution account of the payer,the sixth account can be a financial institution account of the payer,and the funds receiving account can be a third-party payment institutionaccount of the payee.

Referring to the first or second embodiment, the data transmissionbetween the fifth server and the sixth server, and between the fifthserver and the funds receiving server can be performed through anintermediate server. The intermediate server includes but is not limitedto a NETPAY or UNIONPAY server or a server of a payment regulatoryauthority.

In the present embodiment, the third account is bound to the fourthaccount by using the method in the first or second embodiment. This canimplement one-to-many account binding at one single time and improve theefficiency of account binding. Payment through the bound account furtherimproves the payment efficiency.

A sixth embodiment (hereinafter referred to as “the present embodiment”)of the present specification provides a payment method, and an executionbody of the present embodiment can be a terminal device (including butnot limited to a mobile phone, a computer, a pad, and a television), aserver, an operating system, a payment platform, a payment system, etc.,that is, the execution body can be diverse, and the execution body canbe set, used, or transformed as needed. In addition, a third-partyapplication can alternatively be provided to assist the execution bodyin executing the present embodiment. For example, as shown in FIG. 1 ,the payment method in the present embodiment can be performed by aserver, an application (corresponding to the server) can be installed ona terminal device (held by a user), data can be transmitted between theterminal device or the application and the server, and the terminaldevice or the application can be used to collect, input, or output data,or process a page or information (for the user), thereby assisting theserver in performing the payment method in the present embodiment.

As shown in FIG. 15 , the payment method provided in the presentembodiment is applied to a sixth server (that is, the execution body isthe sixth server), and includes the following:

S602: If a payment request sent by a fifth server is obtained, determinea sixth account on the sixth server from which funds are to be deducted,and determine a payment amount.

The sixth server in the present embodiment is equivalent to any one ofthe first to fourth servers, or can be the target server in the secondembodiment. The payment request in the present embodiment is the secondpayment request in the fourth embodiment.

S604: Decrease the funds in the sixth account by the payment amount, andsend payment feedback data to the fifth server, where the sixth accountis bound to a fifth account on the fifth server by using the methoddescribed in the first or second embodiment, the fifth account is a userlogin account on the fifth server, and the fifth account is used toreceive a payment request sent by a terminal device.

For the content not described in detail in the present embodiment,references can be made to the fourth embodiment.

In the present embodiment, the third account is bound to the fourthaccount by using the method in the first or second embodiment. This canimplement one-to-many account binding at one single time and improve theefficiency of account binding. Payment through the bound account furtherimproves the payment efficiency.

It is worthwhile to note that the first and second servers in the firstor second embodiment can be located in different countries or regions(the intermediate server can be located in the same country or region asthe first or second server, or the intermediate server and the first orsecond server can be located in different countries or regions), so asto implement (one-to-many) account binding between different countriesor regions. Likewise, the third and fourth servers (and the intermediateserver) in the third or fourth embodiment, or the fifth and sixthservers (and the intermediate server) in the fifth or sixth embodimentcan also be located in different countries or regions, so as toimplement the resource transfer or payment between different countriesor regions.

As shown in FIG. 16 , a seventh embodiment of the present specificationprovides a data processing apparatus, including the following: apreparatory binding module 701, configured to obtain a user bindingrequest sent by a terminal device, determine a first to-be-bound accounton the apparatus, and send user binding request feedback data to theterminal device so that the terminal device displays candidate bindingobjects; an initial binding module 703, configured to obtain bindingobject selection data sent by the terminal device, determine respectivetarget binding objects based on the binding object selection data, anddetermine one or more target servers among servers corresponding to eachof the respective target binding objects; and an account binding module705, configured to: bind the first account to a second account on eachtarget server, and send an account binding request to each target serverso that the target server binds the second account on the target serverto the first account, where the second account corresponds to the sameuser identity data as the first account.

Optionally, the apparatus further includes a first server, and the firstaccount is an account on the first server.

Optionally, the preparatory binding module 701 is further configured to:before sending an account binding request to each target server, send anidentity authentication request or a binding consulting request to theserver corresponding to respective target binding objects, where theidentity authentication request or the binding consulting requestincludes the user identity data corresponding to the first account, sothat any server corresponding to respective target binding objectsdetermines a second account on the server corresponding to the same useridentity data as the first account.

Optionally, the preparatory binding module 701 is further configured to:after sending the identity authentication request or the bindingconsulting request to any server corresponding to respective targetbinding objects, obtain authentication feedback data or consultationfeedback data sent by any server corresponding to respective targetbinding objects, and determine the second account on the server based onthe authentication feedback data or the consultation feedback data sentby the server.

Optionally, the preparatory binding module 701 is further configured to:after determining the second account on any server corresponding torespective target binding objects based on the authentication feedbackdata or the consultation feedback data sent by the server, and beforedetermining one or more target servers, send candidate account data tothe terminal device, where the candidate account data is used to enablethe terminal device to display the second account that is determined bythe server corresponding to respective target binding objects.

Optionally, the preparatory binding module 701 is further configured to:after the sending an identity authentication request or a bindingconsulting request to any server corresponding to respective targetbinding objects, obtain the authentication feedback data or theconsultation feedback data sent by any server corresponding torespective target binding objects, where if it is determined that thesecond account does not exist on a server corresponding to the targetbinding object, the candidate account data is further used to enable theterminal device to display first prompt information, and the firstprompt information is used to prompt that there is no account that canbe bound to the target binding object corresponding to the server onwhich the second account does not exist.

Optionally, the preparatory binding module 701 is further configured to:after the sending an identity authentication request or a bindingconsulting request to any server corresponding to respective targetbinding objects, obtain the authentication feedback data or theconsultation feedback data sent by any server corresponding torespective target binding objects, where if it is determined that thesecond account does not exist on a server corresponding to the targetbinding object, the candidate account data is further used to enable theterminal device to display second prompt information, and the secondprompt information is further used to prompt a user to create an accountfor the target binding object corresponding to the server on which thesecond account does not exist.

Optionally, the preparatory binding module 701 is further configured to:after the sending candidate account data to the terminal device, obtaina user creation request sent by the terminal device, and determine oneor more account creation servers based on the user creation request; andsend an account creation request to each account creation server, sothat each account creation server creates a second account correspondingto the same user identity data as the first account.

Optionally, the preparatory binding module 701 is further configured to:after the sending an account creation request to each account creationserver, obtain creation feedback data sent by any account creationserver, and determine the second account created by the account creationserver based on the creation feedback data; and send supplementalcandidate account data to the terminal device, where the supplementalcandidate account data is used to enable the terminal device to displaythe second account created by each account creation server.

Optionally, the preparatory binding module 701 is further configured to:after the obtaining authentication feedback data or consultationfeedback data sent by any server corresponding to respective targetbinding objects, determine the second account on the server based on theauthentication feedback data or the consultation feedback data sent bythe server.

Optionally, the candidate account data is further used to enable theterminal device to display first recommendation information, and thefirst recommendation information is used to prompt the second accountrecommended to be bound.

Optionally, the preparatory binding module 701 is further configured to:after determining the second account on any server corresponding torespective target binding objects based on the authentication feedbackdata or the consultation feedback data sent by the server, determine thesecond account recommended to be bound among the second accounts of theserver corresponding to respective target binding objects.

The candidate account data is further used to enable the terminal deviceto display second recommendation information, and the secondrecommendation information is used to prompt the second accountrecommended to be bound.

Optionally, the determining the second account recommended to be boundamong second accounts of the servers corresponding to each of therespective target binding objects includes the following: determiningthe second account recommended to be bound among the second accounts ofthe servers corresponding to each of the respective target bindingobjects, based on historical interaction data between the first serverand the server corresponding to respective target binding objects.

Optionally, for any target server, if there are a plurality of secondaccounts on the target server, the sending an account binding request toeach target server so that the target server binds the second account onthe target server to the first account includes the following: sendingthe account binding request to each target server so that the targetserver binds one second account on the target server to the firstaccount.

Optionally, the determining one or more target servers among serverscorresponding to each of the respective target binding objects includesthe following: obtaining binding account selection data sent by theterminal device, determining one or more selected second accounts basedon the binding account selection data, and using a server on which theone or more selected second accounts are located as the target server.

Optionally, the binding the first account to a second account on eachtarget server, and sending an account binding request to each targetserver so that the target server binds the second account on the targetserver to the first account includes the following: sending the accountbinding request to each target server so that the target server bindsthe second account on the target server to the first account; obtainingaccount binding request feedback data sent by any target server, and ifit is determined, based on the account binding request feedback data,that the target server has bound the second account on the target serverto the first account, binding the first account to the second account onthe target server; or after binding the first account to the secondaccount on any target server, sending the account binding request to thetarget server so that the target server binds the second account on thetarget server to the first account.

Optionally, the apparatus further includes the following: a sendingmodule, configured to send user feedback data to the terminal device sothat the terminal device displays an account binding result.

Optionally, the first account is a login account of the terminal devicewhen the account binding request is obtained; or the first account isdetermined based on the account binding request.

Optionally, the account binding request includes user identity datacorresponding to the first account.

Optionally, the first account or the second account is a resourcestorage account or a resource transfer account.

Optionally, if the first server sends any request or any data to anyserver corresponding to respective target binding objects, the firstserver sends any request or any data to an intermediate server, and theintermediate server sends any request or any data to any servercorresponding to respective target binding objects.

As shown in FIG. 17 , an eighth embodiment of the present specificationprovides a data processing apparatus, including the following: apreparatory binding module 802, configured to: if an identityauthentication request or a binding consulting request sent by a firstserver is obtained, where the identity authentication request or thebinding consulting request includes user identity data corresponding toa first account, determine a second account on the apparatuscorresponding to the same user identity data as the first account, wherethe first account is an account on the first server; and sendauthentication feedback data or consultation feedback data to the firstserver, where the authentication feedback data or the consultationfeedback data includes account data of the second account, so that thefirst server determines one or more target servers and sends an accountbinding request to each target server; and an account binding module804, configured to: if the account binding request sent by the firstserver is obtained, bind the second account to the first account.

Optionally, the apparatus further includes a second server, and thesecond account is an account on the second server.

Optionally, after the identity authentication request or the bindingconsulting request sent by the first server is obtained, if thepreparatory binding module 802 determines that there is no account onthe second server corresponding to the same user identity data as thefirst account, the authentication feedback data or the consultationfeedback data is used to enable the first server to determine that thereis no account on the second server corresponding to the same useridentity data as the first account.

Optionally, the preparatory binding module 802 is further configured to:if an account creation request sent by the first server is received, thesecond account corresponding to the same user identity data as the firstaccount is created based on the account creation request; and creationfeedback data is sent to the first server, where the creation feedbackdata includes the account data of the second account that is createdbased on the account creation request.

Optionally, after the identity authentication request or the bindingconsulting request sent by the first server is obtained, if thepreparatory binding module 802 determines that there are a plurality ofsecond accounts, the authentication feedback data or the consultationfeedback data further includes account data of a recommended account,and the recommended account is one or more second accounts.

Optionally, the preparatory binding module 802 is further configured todetermine the recommended account based on historical account operationdata of the plurality of second accounts.

Optionally, if there are a plurality of second accounts, the binding thesecond account to the first account includes the following: determininga second to-be-bound account among the plurality of second accountsbased on the account binding request, and binding the second to-be-boundaccount to the first account.

Optionally, if there are a plurality of second accounts, the binding thesecond account to the first account includes the following: determininga second to-be-bound account among the plurality of second accounts, andbinding the second to-be-bound account to the first account.

Optionally, the apparatus further includes the following: a sendingmodule, configured to send account binding request feedback data to thefirst server after binding the second account to the first account.

Optionally, if the second server sends any request or any data to thefirst server, the second server sends any request or any data to anintermediate server, and the intermediate server sends any request orany data to the first server.

As shown in FIG. 18 , a ninth embodiment of the present specificationprovides a resource transfer apparatus, including the following: atransfer initiation module 901, configured to obtain a first resourcetransfer request sent by a terminal device, and determine a thirdaccount and a fourth account for which resource transfer is to beperformed, and a resource transfer amount, where the third account is anaccount on the apparatus, and the third account is bound to the fourthaccount by using the method described in the first or second embodiment;and a transfer module 903, configured to send a second resource transferrequest to a fourth server on which the fourth account is located, sothat the fourth server decreases a resource of the fourth account by theresource transfer amount; obtain resource transfer feedback data sent bythe fourth server, and if it is determined, based on the resourcetransfer feedback data, that the resource of the fourth account isdecreased by the resource transfer amount, increase a resource of thethird account by the resource transfer amount; or decrease a resource ofthe third account by the resource transfer amount, and send a secondresource transfer request to a fourth server on which the fourth accountis located, so that the fourth server increases a resource of the fourthaccount by the resource transfer amount.

Optionally, the apparatus further includes a third server, and the thirdaccount is an account on the third server.

As shown in FIG. 19 , a tenth embodiment of the present specificationprovides a resource transfer apparatus, including the following: atransfer acceptance module 1002, configured to: if a resource transferrequest sent by a third server is obtained, determine a fourth accounton the apparatus for which resource transfer is to be performed, anddetermine a resource transfer amount; and a transfer module 1004,configured to decrease a resource of the fourth account by the resourcetransfer amount, and send resource transfer feedback data to the thirdserver, so that the third server increases a resource of a third accountfor which resource transfer is to be performed by the resource transferamount; or if it is determined, based on the resource transfer request,that the third server decreases a resource of a third account for whichresource transfer is to be performed by the resource transfer amount,increase a resource of the fourth account by the resource transferamount, where the third account is an account on the third server, andthe third account is bound to the fourth account by using the methoddescribed in the first or second embodiment.

Optionally, the apparatus further includes a fourth server, and thefourth account is an account on the fourth server.

As shown in FIG. 20 , an eleventh embodiment of the presentspecification provides a payment apparatus, including the following: apayment initiation module 1101, configured to obtain a first paymentrequest sent by a terminal device, and determine a fifth account, asixth account from which funds are to be deducted, and a payment amount,where the fifth account is a user login account on the apparatus, andthe fifth account is bound to the sixth account by using the methoddescribed in the first or second embodiment; and a payment module 1103,configured to send a second payment request to a sixth server on whichthe sixth account is located, so that the sixth server decreases thefunds in the sixth account by the payment amount.

Optionally, the apparatus further includes a fifth server, and the fifthaccount is an account on the fifth server.

As shown in FIG. 21 , a twelfth embodiment of the present specificationprovides a payment apparatus, including the following: a paymentacceptance module 1202, configured to: if a payment request sent by afifth server is obtained, determine a sixth account on the apparatusfrom which funds are to be deducted, and determine a payment amount; anda payment module 1204, configured to decrease the funds in the sixthaccount by the payment amount, and send payment feedback data to thefifth server, where the sixth account is bound to a fifth account on thefifth server by using the method described in the first or secondembodiment, the fifth account is a user login account on the fifthserver, and the fifth account is used to receive a payment request sentby a terminal device.

Optionally, the apparatus further includes a sixth server, and the sixthaccount is an account on the sixth server.

It is worthwhile to note that the apparatus in the seventh or eighthembodiment can be located in different countries or regions (theintermediate server can be located in the same country or region as theapparatus in the seventh or eighth embodiment, or the intermediateserver and the apparatus in the seventh or eighth embodiment can belocated in different countries or regions), so as to implement(one-to-many) account binding between different countries or regions.Likewise, the apparatus (and the intermediate server) in the ninth ortenth embodiment, or the apparatus (and the intermediate server) in theeleventh or twelfth embodiment can also be located in differentcountries or regions, so as to implement the resource transfer orpayment between different countries or regions.

A thirteenth embodiment of the present specification provides a dataprocessing device, including the following: at least one processor; anda memory communicatively connected to the at least one processor, wherethe memory stores an instruction that can be executed by the at leastone processor, and the instruction is executed by the at least oneprocessor to enable the at least one processor to perform the dataprocessing method described in the first or second embodiment.

A fourteenth embodiment of the present specification provides a resourcetransfer device, including the following: at least one processor; and amemory communicatively connected to the at least one processor, wherethe memory stores an instruction that can be executed by the at leastone processor, and the instruction is executed by the at least oneprocessor to enable the at least one processor to perform the resourcetransfer method described in the third or fourth embodiment.

A fifteenth embodiment of the present specification provides a paymentdevice, including the following: at least one processor; and a memorycommunicatively connected to the at least one processor, where thememory stores an instruction that can be executed by the at least oneprocessor, and the instruction is executed by the at least one processorto enable the at least one processor to perform the payment methoddescribed in the fifth or sixth embodiment.

A sixteenth embodiment of the present specification provides acomputer-readable storage medium, where the computer-readable storagemedium stores a computer-executable instruction, and thecomputer-executable instruction is executed by a processor to implementthe data processing method described in the first or second embodiment.

A seventeenth embodiment of the present specification provides acomputer-readable storage medium, where the computer-readable storagemedium stores a computer-executable instruction, and thecomputer-executable instruction is executed by a processor to implementthe resource transfer method described in the third or fourthembodiment.

An eighteenth embodiment of the present specification provides acomputer-readable storage medium, where the computer-readable storagemedium stores a computer-executable instruction, and thecomputer-executable instruction is executed by a processor to implementthe payment method described in the fifth or sixth embodiment.

It is worthwhile to note that the data processing device forimplementing the first embodiment and the data processing device forimplementing the second embodiment can be located in different countriesor regions, so as to implement (one-to-many) account binding betweendifferent countries or regions. Likewise, the resource transfer devicefor implementing the third embodiment, the resource transfer device forimplementing the fourth embodiment, the payment device for implementingthe fifth embodiment, and the payment device for implementing the sixthembodiment can be located in different countries or regions, so as toimplement the resource transfer or payment between different countriesor regions.

It is worthwhile to note that the computer-readable storage medium forimplementing the first embodiment and the computer-readable storagemedium for implementing the second embodiment can be located indifferent countries or regions, so as to implement (one-to-many) accountbinding between different countries or regions. Likewise, thecomputer-readable storage medium for implementing the third embodiment,the computer-readable storage medium for implementing the fourthembodiment, the computer-readable storage medium for implementing thefifth embodiment, and the computer-readable storage medium forimplementing the sixth embodiment can be located in different countriesor regions, so as to implement the resource transfer or payment betweendifferent countries or regions.

The above-mentioned embodiments can be used in combination, and moduleshaving the same name can be the same or different between differentembodiments or within the same embodiment.

The specific embodiments of the present specification have beendescribed above, and other embodiments fall within the scope of theappended claims. In some situations, the actions or steps described inthe claims can be performed in an order different from the order in theembodiments and the desired results can still be achieved. In addition,the processes described in the drawings do not necessarily require aspecific order or sequential order shown in order to achieve the desiredresults. In some implementations, multitasking and parallel processingare also possible or may be advantageous.

The embodiments of the present specification are described in aprogressive way. For same or similar parts of the embodiments, mutualreferences can be made to the embodiments. Each embodiment focuses on adifference from the other embodiments. In particular, the apparatus,device, and non-volatile computer-readable storage medium embodimentsare briefly described because they substantially correspond to themethod embodiments. For related parts, references can be made to thedescriptions of the method embodiments.

The apparatus, the device, and the non-volatile computer-readablestorage medium provided in the embodiments of the present specificationcorrespond to the method. Therefore, the apparatus, the device, and thenon-volatile computer storage medium also have similar advantageoustechnical effects to the corresponding method. Because the advantageoustechnical effects of the method have been described in detail above,descriptions for the advantageous technical effects of the correspondingapparatus, device, and non-volatile computer storage medium are omittedhere for simplicity.

In the 1990s, whether technology improvement is hardware improvement(for example, improvement of a circuit structure, such as a diode, atransistor, or a switch) or software improvement (improvement of amethod procedure) can be clearly distinguished. However, as technologiesdevelop, current improvements of many method procedures can beconsidered as direct improvements to hardware circuit structures. Adesigner usually programs an improved method procedure into a hardwarecircuit, to obtain a corresponding hardware circuit structure.Therefore, a method procedure can be improved by using a hardware entitymodule. For example, a programmable logic device (PLD) (for example, afield programmable gate array (FPGA)) is such an integrated circuit, anda logical function of the programmable logic device is determined by auser through device programming. The designer performs programming to“integrate” a digital system to a PLD without requesting a chipmanufacturer to design and produce an application-specific integratedcircuit chip. In addition, at present, instead of manually manufacturingan integrated chip, this type of programming is mostly implemented byusing “logic compiler” software. The programming is similar to asoftware compiler used to develop and write a program. Original codeneeds to be written in a particular programming language forcompilation. The language is referred to as a hardware descriptionlanguage (HDL). There are many HDLs, such as the Advanced BooleanExpression Language (ABEL), the Altera Hardware Description Language(AHDL), Confluence, the Cornell University Programming Language (CUPL),HDCal, the Java Hardware Description Language (JHDL), Lava, Lola, MyHDL,PALASM, and the Ruby Hardware Description Language (RHDL). Thevery-high-speed integrated circuit hardware description language (VHDL)and Verilog are most commonly used. A person skilled in the art shouldalso understand that a hardware circuit that implements a logical methodprocedure can be readily obtained once the method procedure is logicallyprogrammed by using the several described hardware description languagesand is programmed into an integrated circuit.

A controller can be implemented by using any appropriate method. Forexample, the controller can be a microprocessor or a processor, or acomputer-readable medium that stores computer-readable program code(such as software or firmware) that can be executed by themicroprocessor or the processor, a logic gate, a switch, anapplication-specific integrated circuit (ASIC), a programmable logiccontroller, or a built-in microprocessor. Examples of the controllerinclude but are not limited to the following microprocessors: ARC 625D,Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. Thememory controller can also be implemented as a part of the control logicof the memory. A person skilled in the art also knows that, in additionto implementing the controller by using the computer-readable programcode, logic programming can be performed on method steps to allow thecontroller to implement the same function in forms of the logic gate,the switch, the application-specific integrated circuit, theprogrammable logic controller, and the built-in microcontroller.Therefore, the controller can be considered as a hardware component, andan apparatus configured to implement various functions in the controllercan also be considered as a structure in the hardware component.Alternatively, the apparatus configured to implement various functionscan even be considered as both a software module implementing the methodand a structure in the hardware component.

The system, apparatus, module, or unit illustrated in theabove-mentioned embodiments can be specifically implemented by using acomputer chip or an entity, or can be implemented by using a producthaving a certain function. A typical implementation device is acomputer. Specifically, for example, the computer can be a personalcomputer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigationdevice, an e-mail device, a game console, a tablet computer, a wearabledevice, or any combination of these devices.

For ease of description, the above-mentioned apparatus is described bydividing functions into various units. Certainly, functions of the unitscan be implemented in one or more pieces of software and/or hardwarewhen the present specification is implemented.

A person skilled in the art should understand that the embodiments ofthe present specification can be provided as methods, systems, orcomputer program products. Therefore, the embodiments of the presentspecification can use a form of hardware only embodiments, software onlyembodiments, or embodiments with a combination of software and hardware.Moreover, the embodiments of the present specification can use a form ofa computer program product that is implemented on one or morecomputer-usable storage media (including but not limited to a diskmemory, a CD-ROM, an optical memory, etc.) that include computer-usableprogram code.

The present specification is described with reference to the flowchartsand/or block diagrams of the method, the device (system), and thecomputer program product based on the embodiments of the presentspecification. It should be understood that computer programinstructions can be used to implement each process and/or each block inthe flowcharts and/or the block diagrams and a combination of a processand/or a block in the flowcharts and/or the block diagrams. Thesecomputer program instructions can be provided for a general-purposecomputer, a dedicated computer, an embedded processor, or a processor ofanother programmable data processing device to generate a machine, sothe instructions executed by the computer or the processor of theanother programmable data processing device generate an apparatus forimplementing a specific function in one or more processes in theflowcharts and/or in one or more blocks in the block diagrams.

These computer program instructions can be stored in a computer-readablememory that can instruct the computer or the another programmable dataprocessing device to work in a specific way, so the instructions storedin the computer-readable memory generate an artifact that includes aninstruction apparatus. The instruction apparatus implements a specificfunction in one or more processes in the flowcharts and/or in one ormore blocks in the block diagrams.

These computer program instructions can alternatively be loaded onto thecomputer or another programmable data processing device, so that aseries of operations and steps are performed on the computer or theanother programmable device, thereby generating computer-implementedprocessing. Therefore, the instructions executed on the computer or theanother programmable device provide steps for implementing a specificfunction in one or more processes in the flowcharts and/or in one ormore blocks in the block diagrams.

In a typical configuration, a computing device includes one or moreprocessors (CPUs), one or more input/output interfaces, one or morenetwork interfaces, and one or more memories.

The memory may include a non-persistent memory, a random access memory(RAM), a non-volatile memory, and/or another form that are in acomputer-readable medium, for example, a read-only memory (ROM) or aflash memory (flash RAM). The memory is an example of thecomputer-readable medium.

The computer-readable medium includes persistent, non-persistent,movable, and unmovable media that can store information by using anymethod or technology. The information can be a computer-readableinstruction, a data structure, a program module, or other data. Examplesof the computer storage medium include but are not limited to a phasechange random access memory (PRAM), a static RAM (SRAM), a dynamic RAM(DRAM), a RAM of another type, a ROM, an electrically erasableprogrammable ROM (EEPROM), a flash memory or another memory technology,a CD-ROM, a digital versatile disc (DVD), or another optical storage, acassette, a magnetic disk storage, or another magnetic storage device orany other non-transmission medium. The computer storage medium can beconfigured to store information that can be accessed by a computingdevice. Based on the definition in the present specification, thecomputer-readable medium does not include transitory media such as amodulated data signal and carrier.

It is worthwhile to further note that, the terms “include”, “comprise”,or their any other variants are intended to cover a non-exclusiveinclusion, so a process, a method, a product or a device that includes alist of elements not only includes those elements but also includesother elements which are not expressly listed, or further includeselements inherent to such process, method, product or device. Withoutmore constraints, an element preceded by “includes a . . . ” does notpreclude the existence of additional identical elements in the process,method, product or device that includes the element.

The present specification can be described in the general context ofcomputer-executable instructions executed by a computer, for example, aprogram module. Generally, the program module includes a routine, aprogram, an object, a component, a data structure, etc. executing aspecific task or implementing a specific abstract data type. The presentspecification can alternatively be practiced in distributed computingenvironments in which tasks are performed by remote processing devicesthat are connected through a communications network. In a distributedcomputing environment, the program module can be located in both localand remote computer storage media including storage devices.

The embodiments of the present specification are described in aprogressive way. For same or similar parts of the embodiments, mutualreferences can be made to the embodiments. Each embodiment focuses on adifference from the other embodiments. Particularly, the systemembodiments are briefly described because they substantially correspondto the method embodiments. For related parts, references can be made torelated descriptions in the method embodiments.

The above-mentioned descriptions are merely embodiments of the presentspecification, and are not intended to limit the present application. Aperson skilled in the art can make various modifications and changes tothe present application. Any modification, equivalent replacement, orimprovement made without departing from the spirit and principle of thepresent application shall fall within the scope of the claims in thepresent application.

What is claimed is:
 1. A computer-implemented method, comprising:obtaining, from a first server and by a second server, an identityauthentication request or a binding consulting request, wherein theidentity authentication request or the binding consulting requestcomprises user identity data corresponding to a first account on thefirst server; in response to obtaining the identity authenticationrequest or the binding consulting request, determining one or moresecond accounts on the second server that correspond to the same useridentity data as the first account; sending, by the second server and tothe first server, authentication feedback data or consultation feedbackdata, wherein the authentication feedback data or the consultationfeedback data comprises account data of the one or more second accounts,so that the first server determines one or more target servers andsends, to each target server, a respective account binding request;obtaining, by the second server, an account binding request sent by thefirst server; and in response to obtaining the account binding request,binding, by the second server, at least one of the one or more secondaccounts to the first account.
 2. The computer-implemented method ofclaim 1, wherein the authentication feedback data or the consultationfeedback data enables the first server to determine whether there is anaccount on the second server that corresponds to the same user identitydata as the first account.
 3. The computer-implemented method of claim1, further comprising: obtaining, from the first server and by thesecond server, an account creation request; in response to obtaining theaccount creation request, creating, on the second server, a secondaccount that corresponds to the same user identity data as the firstaccount; and sending, by the second server and to the first server,creation feedback data that comprises the account data of the secondaccount that has been created in response to obtaining the accountcreation request.
 4. The computer-implemented method of claim 1, whereinwhen a plurality of second accounts are on the second server thatcorrespond to the same user identity data as the first account, theauthentication feedback data or the consultation feedback data comprisesaccount data of one or more recommended accounts of the plurality ofsecond accounts.
 5. The computer-implemented method of claim 4, whereina recommended account is determined based on historical accountoperation data of the plurality of second accounts.
 6. Thecomputer-implemented method of claim 1, wherein when a plurality ofsecond accounts are on the second server that correspond to the sameuser identity data as the first account, binding at least one of the oneor more second accounts to the first account comprises: determining asecond to-be-bound account among the plurality of second accounts basedon the account binding request, and binding the second to-be-boundaccount to the first account.
 7. The computer-implemented method ofclaim 1, wherein when a plurality of second accounts are on the secondserver that correspond to the same user identity data as the firstaccount, binding at least one of the one or more second accounts to thefirst account comprises: determining a second to-be-bound account amongthe plurality of second accounts, and binding the second to-be-boundaccount to the first account.
 8. The computer-implemented method ofclaim 1, further comprising: after binding at least one of the one ormore second accounts to the first account, sending, by the second serverand to the first server, account binding request feedback data.
 9. Thecomputer-implemented method of claim 1, wherein when the second serversends any request or any data to the first server, the second serversends any request or any data to an intermediate server for forwardingto the second server.
 10. A non-transitory, computer-readable mediumstoring one or more instructions executable by a computer system toperform operations comprising: obtaining, from a first server and by asecond server, an identity authentication request or a bindingconsulting request, wherein the identity authentication request or thebinding consulting request comprises user identity data corresponding toa first account on the first server; in response to obtaining theidentity authentication request or the binding consulting request,determining one or more second accounts on the second server thatcorrespond to the same user identity data as the first account; sending,by the second server and to the first server, authentication feedbackdata or consultation feedback data, wherein the authentication feedbackdata or the consultation feedback data comprises account data of the oneor more second accounts, so that the first server determines one or moretarget servers and sends, to each target server, a respective accountbinding request; obtaining, by the second server, an account bindingrequest sent by the first server; and in response to obtaining theaccount binding request, binding, by the second server, at least one ofthe one or more second accounts to the first account.
 11. Thecomputer-readable medium of claim 10, wherein the authenticationfeedback data or the consultation feedback data enables the first serverto determine whether there is an account on the second server thatcorresponds to the same user identity data as the first account.
 12. Thecomputer-readable medium of claim 10, the operations further comprising:obtaining, from the first server and by the second server, an accountcreation request; in response to obtaining the account creation request,creating, on the second server, a second account that corresponds to thesame user identity data as the first account; and sending, by the secondserver and to the first server, creation feedback data that comprisesthe account data of the second account that has been created in responseto obtaining the account creation request.
 13. The computer-readablemedium of claim 10, wherein when a plurality of second accounts are onthe second server that correspond to the same user identity data as thefirst account, the authentication feedback data or the consultationfeedback data comprises account data of one or more recommended accountsof the plurality of second accounts.
 14. The computer-readable medium ofclaim 10, the operations further comprising: after binding at least oneof the one or more second accounts to the first account, sending, by thesecond server and to the first server, account binding request feedbackdata.
 15. A computer-implemented system, comprising: one or morecomputers; and one or more computer memory devices interoperably coupledwith the one or more computers and having tangible, non-transitory,machine-readable media storing one or more instructions that, whenexecuted by the one or more computers, perform one or more operationscomprising: obtaining, from a first server and by a second server, anidentity authentication request or a binding consulting request, whereinthe identity authentication request or the binding consulting requestcomprises user identity data corresponding to a first account on thefirst server; in response to obtaining the identity authenticationrequest or the binding consulting request, determining one or moresecond accounts on the second server that correspond to the same useridentity data as the first account; sending, by the second server and tothe first server, authentication feedback data or consultation feedbackdata, wherein the authentication feedback data or the consultationfeedback data comprises account data of the one or more second accounts,so that the first server determines one or more target servers andsends, to each target server, a respective account binding request;obtaining, by the second server, an account binding request sent by thefirst server; and in response to obtaining the account binding request,binding, by the second server, at least one of the one or more secondaccounts to the first account.
 16. The computer-implemented system ofclaim 15, wherein the authentication feedback data or the consultationfeedback data enables the first server to determine whether there is anaccount on the second server that corresponds to the same user identitydata as the first account.
 17. The computer-implemented system of claim15, the operations further comprising: obtaining, from the first serverand by the second server, an account creation request; in response toobtaining the account creation request, creating, on the second server,a second account that corresponds to the same user identity data as thefirst account; and sending, by the second server and to the firstserver, creation feedback data that comprises the account data of thesecond account that has been created in response to obtaining theaccount creation request.
 18. The computer-implemented system of claim15, wherein when a plurality of second accounts are on the second serverthat correspond to the same user identity data as the first account, theauthentication feedback data or the consultation feedback data comprisesaccount data of one or more recommended accounts of the plurality ofsecond accounts.
 19. The computer-implemented system of claim 15, theoperations further comprising: after binding at least one of the one ormore second accounts to the first account, sending, by the second serverand to the first server, account binding request feedback data.